🔧 chore(deps): bump pnpm to 11.17.0 - #42
Merged
Merged
Conversation
- 🔧 keep the package manager current within pnpm 11
|
✅ Approved Straightforward pnpm version bump (11.15.1 → 11.17.0) with updated integrity hash. No new findings.
|
|
| Filename | Overview |
|---|---|
| package.json | packageManager 字段已一致更新为 pnpm 11.17.0 及对应的 SHA-512 integrity pin，未发现具体可达的故障。 |
Reviews (1): Last reviewed commit: "🔧 chore(deps): bump pnpm to 11.17.0" | Re-trigger Greptile
There was a problem hiding this comment.
Pull request overview
Updates the repository’s pinned package manager version in package.json to move pnpm forward within the same major version, ensuring installs use the intended pnpm binary + integrity.
Changes:
- Bump
packageManagerfrom pnpm11.15.1to11.17.0. - Refresh the
sha512integrity suffix associated with thepackageManagerpin.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Validation
Risk
This is a same-major package-manager update. The repository already targets Node.js 22 or newer, so no breaking migration is expected.